Hostname
criminalbackground.com
Last fetched
criminalbackground.com resolves to 96.45.118.30, announced in 96.45.116.0/22 by ASN-FLEXENTIAL - Flexential Colorado Corp. in US. criminalbackground.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
- 96.45.118.30
96.45.116.0/22 · ASN-FLEXENTIAL - Flexential Colorado Corp. · St. Petersburg, US
IPv6 resolution
No AAAA record for criminalbackground.com is recorded in WhisperGraph.
Attribution
flexential colorado
ORIGIN_AS
WHOIS identity
- Registrar
- iana:2
- Registrant organisation
- first advantage
- Contact emails
- domain-admin@fadv.com
Subdomains
Showing 2 of 2 subdomains (2 per page).
Mail and authentication
Nameservers
- ns1.ams.fadv.com
- ns1.blr.fadv.com
- ns3.ind.fadv.com
- ns4.ind.fadv.com
MX records
- criminalbackground-com.mail.protection.outlook.com
SPF policy
- ip: 148.105.0.0/16
- ip: 198.2.128.0/18
- ip: 205.201.128.0/20
- include: zcsend.net.cn
- a: billtrust.com
- include: spf.protection.outlook.com
- include: servers.mcsv.net
- ip: 104.211.201.25
- ip: 104.211.217.254
- ip: 198.73.226.115
- ip: 198.73.226.15
- ip: 198.73.226.26
- ip: 198.73.226.27
- ip: 198.73.226.29
- ip: 198.73.226.94
- ip: 198.73.226.95
- ip: 198.73.226.99
- ip: 198.73.227.153
- ip: 198.73.227.156
- ip: 198.73.227.53
- ip: 202.45.10.175
- ip: 202.45.10.20
- ip: 202.45.10.205
- ip: 202.45.10.45
- ip: 202.45.10.98
- ip: 202.45.11.130
- ip: 202.45.11.150
- ip: 202.45.11.25
- ip: 202.45.11.26
- ip: 202.45.11.27
- ip: 202.45.11.80
- ip: 202.45.11.85
- ip: 203.149.64.130
- ip: 216.234.133.117
- ip: 216.234.133.127
- ip: 216.234.133.171
- ip: 216.234.133.204
- ip: 216.234.133.213
- ip: 216.234.133.214
- ip: 216.234.133.229
- ip: 216.234.133.55
- ip: 216.234.133.56
- ip: 59.160.3.130
Threat-feed evidence
History
Related pages
Pivot from criminalbackground.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: "criminalbackground.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.