Hostname
laodoca.com
Last fetched
laodoca.com resolves to 13.250.77.139, announced in 13.250.0.0/15 by AMAZON-02 - Amazon.com, Inc. in SG. laodoca.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.250.77.139
13.250.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 13.250.86.176
13.250.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 13.250.94.10
13.250.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 18.136.114.253
18.136.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 18.136.136.169
18.136.0.0/16 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 18.138.223.233
18.138.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 18.142.52.141
18.142.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 3.1.65.59
3.0.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 46.137.206.161
46.137.192.0/19 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 47.131.16.59
47.128.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 52.220.177.112
52.220.0.0/15 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 54.254.25.70
54.254.0.0/17 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 47.131.87.16
47.128.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
- 47.128.84.14
47.128.0.0/14 · AMAZON-02 - Amazon.com, Inc. · Singapore, SG
IPv6 resolution
No AAAA record for laodoca.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:120
Subdomains
Showing 3 of 4. View all subdomains →
Mail and authentication
Nameservers
- ns-210.awsdns-26.com
- ns-785.awsdns-34.net
- capricorn.dnspod.net
- nanny.dnspod.net
- ns-1125.awsdns-12.org
- ns-1973.awsdns-54.co.uk
MX records
- mx-n.global-mail.cn
- mx1-n.global-mail.cn
SPF policy
- include: spfv.global-mail.cn
Threat-feed evidence
History
Related pages
Pivot from laodoca.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: "laodoca.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.