Hostname
keywert.com
Last fetched
keywert.com resolves to 13.124.188.211, announced in 13.124.0.0/16 by AMAZON-02 - Amazon.com, Inc. in KR. keywert.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 13.124.188.211
13.124.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Seoul, KR
- 13.125.16.253
13.125.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Seoul, KR
- 3.34.152.233
3.34.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 3.37.187.68
3.36.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 3.39.37.137
3.36.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 43.200.16.226
43.200.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 52.78.243.220
52.78.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Seoul, KR
- 54.180.6.11
54.180.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 43.202.14.200
43.200.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Incheon, KR
- 54.116.251.141
- 54.116.10.120
- 54.116.6.237
IPv6 resolution
No AAAA record for keywert.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:244
- Registrant organisation
- wert intelligence
- Contact emails
- yunpat81@gmail.com
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- ns-35.awsdns-04.com
- ns-709.awsdns-24.net
- ns-1332.awsdns-38.org
- ns-2031.awsdns-61.co.uk
MX records
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- alt3.aspmx.l.google.com
- alt4.aspmx.l.google.com
- smtp.google.com
SPF policy
- include: mail.stibee.com
- include: _spf1.mailnara.co.kr
- include: _spf2.mailnara.co.kr
- include: _spf3.mailnara.co.kr
- include: _spf4.mailnara.co.kr
- include: _spf5.mailnara.co.kr
Threat-feed evidence
History
Related pages
Pivot from keywert.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "keywert.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.