Skip to content

Hostname

selfiescorts.com

Last fetched

selfiescorts.com resolves to 104.26.12.29, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. selfiescorts.com 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 · selfiescorts.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/selfiescorts.com

Resolution chain

IPv6 resolution

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

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:48
Registrant organisation
gabyt durante
Contact emails
losdominiosquetengo@gmail.com

Subdomains

Subdomain
253bdfdcc9f5.selfiescorts.com
mail.selfiescorts.com
mailadmin.selfiescorts.com
webmail.selfiescorts.com
www.selfiescorts.com

Showing 5 of 6. 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

  • hal.ns.cloudflare.com
  • violet.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

  • _dc-mx.253bdfdcc9f5.selfiescorts.com
  • safari.mxrouting.net
  • safari-relay.mxrouting.net

SPF policy

  • include: mxlogin.com
  • a: selfiescorts.com
  • mx: selfiescorts.com
  • a: obelisco.alojandoargentina.net
  • ip: 158.69.114.61

Threat-feed evidence

History

Related pages

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