Skip to content

Hostname

citiescort.com

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1068
Registrant organisation
domain admin
Contact emails
keetat@hotmail.com, 8b85245466ff4d50ac4d57b3523e8aef.protect@withheldforprivacy.com, citiescort.com-owner-mkca@customers.whoisprivacycorp.com, 202ess5v0sw41dwlwjd9@a.o-w-o.info, 6uqw1kq9t2o0awhtx1hp@s.o-w-o.info

Subdomains

Subdomain
agri.citiescort.com
akcaabat.citiescort.com
amasya.citiescort.com
ankara.citiescort.com
antakya.citiescort.com
ardahan.citiescort.com
ayvalik.citiescort.com
bahcesehir.citiescort.com
bayburt.citiescort.com
burdur.citiescort.com
cankaya.citiescort.com
corlu.citiescort.com

Showing 12 of 103. 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

Mail and authentication

Nameservers

  • amir.ns.cloudflare.com
  • cartman.ns.cloudflare.com
  • kenia.ns.cloudflare.com
  • nelci.ns.cloudflare.com

MX records

  • route1.mx.cloudflare.net
  • route2.mx.cloudflare.net
  • route3.mx.cloudflare.net

SPF policy

  • include: _spf.mx.cloudflare.net

Threat-feed evidence

History

Related pages

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