Skip to content

Hostname

protectorfiresafety.com

Last fetched

protectorfiresafety.com resolves to 66.116.198.136, announced in 66.116.198.0/23 by ORACLE-BMC-31898 - Oracle Corporation in IN. protectorfiresafety.com is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Categories: Phishing

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:45:24 GMT
Last seen on a feed
Mon, 21 Sep 2026 20:22:44 GMT

Nutrition Label

WHISPER CANON · protectorfiresafety.comRouting diversity1.5/10Peering density8.4/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency10.0/10Resolver footprint4.0/10canon.whisper.security/host/protectorfiresafety.com

Resolution chain

IPv6 resolution

No AAAA record for protectorfiresafety.com is recorded in WhisperGraph.

Attribution

oracle

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,
Contact emails
sales@protectorfiresafety.com, shyamal.smc@gmail.com

Subdomains

Subdomain
mail.protectorfiresafety.com
ns1.protectorfiresafety.com
ns2.protectorfiresafety.com
server.protectorfiresafety.com
www.protectorfiresafety.com

Showing 5 of 5 subdomains (5 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ns1.foundryportal.com
  • ns1.protectorfiresafety.com
  • ns2.protectorfiresafety.com

MX records

  • protectorfiresafety.com

SPF policy

  • a: protectorfiresafety.com
  • mx: protectorfiresafety.com
  • include: eig.spf.a.cloudfilter.net
  • ip: 66.116.198.136

Threat-feed evidence

History

Related pages

Pivot from protectorfiresafety.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: "protectorfiresafety.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.