🌐 https://www.jpcert.or.jp/wr/2026/wr260805.html#4
URL
· host
www.jpcert.or.jp
· threat 0.50 (HIGH)
· CERT Advisories First seen 2026-08-06 13:14:06 · last seen 2026-08-06 14:46:06
🔄 Pivot:📁 CERT Advisories
Threat score
0.50
MEDIUM
Sightings
2
1 sources
Subdomains (local)
0
from indicators
Related IPs
20
A/AAAA records
DNS records (local)
18
5 types
Reporting sources
1
0 enrichments
📡 Reporting-source breakdown
1
1 total source links on this indicator.
🏷 Tag breakdown (domain family)
No data.
📈 DNS record-type counts
8
4
4
1
1
📅 First-seen timeline (family)
1
🏷 WHOIS / Registration (local cache)
No cached WHOIS for www.jpcert.or.jp. Resolve & cache.
📡 DNS Records
Stored (local dns_records) — 18
| Type | Value | TTL | Checked |
|---|---|---|---|
| A | 65.8.20.86 |
60 | 2026-08-06 |
| A | 65.8.20.75 |
60 | 2026-08-06 |
| A | 65.8.20.126 |
60 | 2026-08-06 |
| A | 65.8.20.53 |
60 | 2026-08-06 |
| AAAA | 2600:9000:2105:c200:2:f996:9600:93a1 |
60 | 2026-08-06 |
| AAAA | 2600:9000:2105:b200:2:f996:9600:93a1 |
60 | 2026-08-06 |
| AAAA | 2600:9000:2105:a200:2:f996:9600:93a1 |
60 | 2026-08-06 |
| AAAA | 2600:9000:2105:8a00:2:f996:9600:93a1 |
60 | 2026-08-06 |
| AAAA | 2600:9000:2105:d400:2:f996:9600:93a1 |
60 | 2026-08-06 |
| AAAA | 2600:9000:2105:3200:2:f996:9600:93a1 |
60 | 2026-08-06 |
| AAAA | 2600:9000:2105:c600:2:f996:9600:93a1 |
60 | 2026-08-06 |
| AAAA | 2600:9000:2105:5000:2:f996:9600:93a1 |
60 | 2026-08-06 |
| CNAME | d81drv6iivfiw.cloudfront.net |
300 | 2026-08-06 |
| NS | ns-1144.awsdns-15.org |
348 | 2026-08-06 |
| NS | ns-462.awsdns-57.com |
348 | 2026-08-06 |
| NS | ns-1621.awsdns-10.co.uk |
348 | 2026-08-06 |
| NS | ns-602.awsdns-11.net |
348 | 2026-08-06 |
| SOA | ns-1621.awsdns-10.co.uk |
60 | 2026-08-06 |
Live (DNS-over-HTTPS · optional augmentation)
| Type | Value | TTL |
|---|---|---|
| A | d81drv6iivfiw.cloudfront.net. |
300 |
| A | 65.8.20.126 |
60 |
| A | 65.8.20.86 |
60 |
| A | 65.8.20.53 |
60 |
| A | 65.8.20.75 |
60 |
| AAAA | d81drv6iivfiw.cloudfront.net. |
300 |
| AAAA | 2600:9000:2105:cc00:2:f996:9600:93a1 |
60 |
| AAAA | 2600:9000:2105:6800:2:f996:9600:93a1 |
60 |
| AAAA | 2600:9000:2105:9800:2:f996:9600:93a1 |
60 |
| AAAA | 2600:9000:2105:2c00:2:f996:9600:93a1 |
60 |
| AAAA | 2600:9000:2105:c00:2:f996:9600:93a1 |
60 |
| AAAA | 2600:9000:2105:a400:2:f996:9600:93a1 |
60 |
| AAAA | 2600:9000:2105:9c00:2:f996:9600:93a1 |
60 |
| AAAA | 2600:9000:2105:2e00:2:f996:9600:93a1 |
60 |
| MX | d81drv6iivfiw.cloudfront.net. |
300 |
| NS | d81drv6iivfiw.cloudfront.net. |
300 |
| NS | ns-462.awsdns-57.com. |
21600 |
| NS | ns-1144.awsdns-15.org. |
21600 |
| NS | ns-602.awsdns-11.net. |
21600 |
| NS | ns-1621.awsdns-10.co.uk. |
21600 |
| TXT | d81drv6iivfiw.cloudfront.net. |
299 |
| CNAME | d81drv6iivfiw.cloudfront.net. |
299 |
🖥 Related IPs (20)
Resolved from local A/AAAA records (augmented with live DoH when reachable). Each pivots to its IP dossier.
65.8.20.86 →
65.8.20.75 →
65.8.20.126 →
65.8.20.53 →
2600:9000:2105:c200:2:f996:9600:93a1 →
2600:9000:2105:b200:2:f996:9600:93a1 →
2600:9000:2105:a200:2:f996:9600:93a1 →
2600:9000:2105:8a00:2:f996:9600:93a1 →
2600:9000:2105:d400:2:f996:9600:93a1 →
2600:9000:2105:3200:2:f996:9600:93a1 →
2600:9000:2105:c600:2:f996:9600:93a1 →
2600:9000:2105:5000:2:f996:9600:93a1 →
2600:9000:2105:cc00:2:f996:9600:93a1 →
2600:9000:2105:6800:2:f996:9600:93a1 →
2600:9000:2105:9800:2:f996:9600:93a1 →
2600:9000:2105:2c00:2:f996:9600:93a1 →
2600:9000:2105:c00:2:f996:9600:93a1 →
2600:9000:2105:a400:2:f996:9600:93a1 →
2600:9000:2105:9c00:2:f996:9600:93a1 →
2600:9000:2105:2e00:2:f996:9600:93a1 →
🌐 Subdomains — local intel (0)
No subdomains of www.jpcert.or.jp in local intel. Check crt.sh ↗
📡 Reporting Sources (1)
JPCERT/CC (JP) | CERT Advisories |
🌐 Same-ASN domains (0)
No ASN linkage in local intel.
🔍 OSINT pivots — external lookups
🔗 Internal pivots & actions
Every panel resolves local-first: threat, category, first-seen & sightings from
indicators; DNS from dns_records; WHOIS from whois_cache; subdomains via bounded suffix match on indicators; related IPs from A/AAAA records; tags, reporting sources and the link graph from the local relations. Live OTX pulses and DNS-over-HTTPS are optional augmentation and their absence never blanks the dossier.
Workstation · Copilot · AI Skills · Automation · Playbooks · Lookups · Docs · Reports
🤖 AI Copilot
⚡ AI Skills
🔍 Lookup & Enrich
📚 Docs & Reports
💡 Recommendations
- Audit DNS to build passive history
- Pivot resolved IPs to their dossiers
- Report phishing to registrar/host