Hostname
puresafety.com
Last fetched
puresafety.com resolves to 16.15.177.8, announced in 16.15.176.0/21 by AMAZON-AES - Amazon.com, Inc. in US. puresafety.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
- 16.15.177.8
16.15.176.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.183.109
16.15.176.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.183.11
16.15.176.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.183.127
16.15.176.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.183.166
16.15.176.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.183.171
16.15.176.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.183.198
16.15.176.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.183.200
16.15.176.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.183.6
16.15.176.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.183.72
16.15.176.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.191.143
16.15.184.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.191.186
16.15.184.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.193.186
16.15.192.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.199.20
16.15.192.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.199.211
16.15.192.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.199.216
16.15.192.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.199.22
16.15.192.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.199.40
16.15.192.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.207.141
16.15.200.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
- 16.15.207.160
16.15.200.0/21 · AMAZON-AES - Amazon.com, Inc. · Ashburn, US
IPv6 resolution
No AAAA record for puresafety.com is recorded in WhisperGraph.
Attribution
Aws
cloud · ORIGIN_AS
WHOIS identity
- Registrar
- iana:468
- Registrant organisation
- on behalf of puresafety.com owner
- Contact emails
- sebastian.haupt@puresafety.com, elaine.wilder@ul.com, 0a69a0fd-1b94-4ee0-bae8-8d05f63ce0a7@identity-protect.org, 2de4e433-a96c-4a56-9178-4c92c3d3d217@identity-protect.org, a84ed8dd-7442-4250-b5c2-92b7a6fecc81@identity-protect.org, e5a923d4-a30d-40b5-8d9f-133fde25a7ca@identity-protect.org, e630b0e0-b019-40c0-9a28-a9b87faff17a@identity-protect.org, eea075f5-f176-4cbc-bbd5-b5d0ccb75fb2@identity-protect.org, owner-10090938@puresafety.com.whoisprivacyservice.org, owner-1163413@puresafety.com.whoisprivacyservice.org, owner-1402787@puresafety.com.whoisprivacyservice.org, owner-2066146@puresafety.com.whoisprivacyservice.org, owner-4532769@puresafety.com.whoisprivacyservice.org, owner-4754035@puresafety.com.whoisprivacyservice.org, owner-5486396@puresafety.com.whoisprivacyservice.org, owner-5668378@puresafety.com.whoisprivacyservice.org, owner-5756345@puresafety.com.whoisprivacyservice.org, owner-6259170@puresafety.com.whoisprivacyservice.org, owner-6296243@puresafety.com.whoisprivacyservice.org, owner-8891246@puresafety.com.whoisprivacyservice.org
Subdomains
Showing 12 of 76. View all subdomains →
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Mail and authentication
Nameservers
- ns-503.awsdns-62.com
- ns-701.awsdns-23.net
- ns-1076.awsdns-06.org
- ns-1693.awsdns-19.co.uk
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- post.puresafety.com
- smtp.puresafety.com
- smtp2.puresafety.com
- smtp3.puresafety.com
SPF policy
- ip: 66.18.116.43/32
- include: jobvite.com
- ip: 12.19.100.5
- ip: 12.19.100.52
- ip: 64.154.30.130
- ip: 66.18.116.143
- ip: 66.18.116.4
Threat-feed evidence
History
Related pages
Pivot from puresafety.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: "puresafety.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.