Hostname
confirma.do
Last fetched
confirma.do resolves to 18.235.178.100, announced in 18.232.0.0/14 by AMAZON-AES - Amazon.com, Inc. in US. confirma.do 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.235.178.100
18.232.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.225.14.202
3.224.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.196.89.31
34.192.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 34.197.32.111
34.192.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 44.208.59.157
44.192.0.0/11 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 44.209.194.115
44.192.0.0/11 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.22.65.30
52.20.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.225.186.228
54.224.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.236.89.4
54.236.64.0/18 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 98.95.132.185
98.88.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.174.105.5
54.174.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 32.199.127.186
32.196.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 32.194.23.30
32.192.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for confirma.do is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for confirma.do. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.
Mail and authentication
Nameservers
- ns10.digicertdns.com
- ns11.digicertdns.com
- ns12.digicertdns.com
- ns13.digicertdns.net
- ns14.digicertdns.net
- ns15.digicertdns.net
Threat-feed evidence
History
Related pages
Pivot from confirma.do 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: "confirma.do"})-[: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.