Hostname
adortaxpay.com
Last fetched
adortaxpay.com resolves to 18.238.80.27, announced in 18.238.80.0/23 by AMAZON-02 - Amazon.com, Inc. in US. adortaxpay.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
- 18.238.80.27
18.238.80.0/23 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.80.30
18.238.80.0/23 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.80.54
18.238.80.0/23 · AMAZON-02 - Amazon.com, Inc. · New York, US
- 18.238.80.8
18.238.80.0/23 · AMAZON-02 - Amazon.com, Inc. · New York, US
IPv6 resolution
No AAAA record for adortaxpay.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:2
- Registrant organisation
- on behalf of adortaxpay.com owner
- Contact emails
- domain.operations@tylertech.com, 01c669f5-aa60-4ac8-a7c5-c4ef26895bd6@identity-protect.org, 0abafc02-aa6a-47d1-a2e2-49313fb2406c@identity-protect.org, 734db3ff-af8e-4186-833f-00cca4c4886b@identity-protect.org, 969e0557-c790-4cd6-930d-324290c4f2c0@identity-protect.org, ebbe8865-15f9-4ee4-b02c-eebfeef9e9f7@identity-protect.org, owner-1031051@adortaxpay.com.whoisprivacyservice.org
Subdomains
Showing 3 of 6. View all subdomains →
Mail and authentication
Nameservers
- ns-106.awsdns-13.com
- ns-189.awsdns-23.com
- ns-682.awsdns-21.net
- ns-903.awsdns-48.net
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
- ns-1359.awsdns-41.org
- ns-1504.awsdns-60.org
- ns-1737.awsdns-25.co.uk
- ns-1898.awsdns-45.co.uk
Threat-feed evidence
History
Related pages
Pivot from adortaxpay.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: "adortaxpay.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.