Skip to content

Hostname

britsafe.in

Last fetched

britsafe.in resolves to 104.21.17.27, announced in 104.21.16.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. britsafe.in is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · britsafe.inRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.0/10canon.whisper.security/host/britsafe.in

Resolution chain

IPv6 resolution

No AAAA record for britsafe.in is recorded in WhisperGraph.

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:106
Registrant organisation
british safety council

Subdomains

Subdomain
mktg.britsafe.in
www.britsafe.in

Showing 2 of 3. 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.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • gabe.ns.cloudflare.com
  • vera.ns.cloudflare.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • britsafe-in.mail.protection.outlook.com

SPF policy

  • ip: 185.53.93.48/28
  • include: mktomail.com
  • include: spf.protection.outlook.com
  • include: _spf.salesforce.com
  • include: mail.zendesk.com
  • mx: britsafe.in
  • include: spf.exclaimer.net
  • include: spf.mailanyone.net
  • include: mailgun.org
  • ip: 162.13.152.98
  • ip: 18.130.53.53
  • ip: 18.169.234.25
  • ip: 35.176.209.243
  • ip: 50.57.222.104

Threat-feed evidence

History

Related pages

Pivot from britsafe.in 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: "britsafe.in"})-[: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.