Hostname
api.policescanner.us
Last fetched
api.policescanner.us resolves to 100.51.60.151, announced in 100.48.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. api.policescanner.us 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
- 100.51.60.151
100.48.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 18.233.56.212
18.232.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.213.136.130
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.214.202.36
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 3.216.43.204
3.208.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.203.22.207
52.200.0.0/13 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.21.107.5
52.20.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 52.54.76.49
52.54.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.146.109.14
54.144.0.0/14 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.172.230.163
54.172.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 54.225.113.226
54.224.0.0/15 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 100.62.17.27
100.48.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 100.60.32.21
100.48.0.0/12 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 184.192.22.45
- 100.49.69.129
IPv6 resolution
No AAAA record for api.policescanner.us is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for api.policescanner.us. 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
- ns-318.awsdns-39.com
- ns-926.awsdns-51.net
- ns-1441.awsdns-52.org
- ns-1622.awsdns-10.co.uk
Threat-feed evidence
History
Related pages
Pivot from api.policescanner.us 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: "api.policescanner.us"})-[: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.