Skip to content

Hostname

twitive.com

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1387
Registrant organisation
c/o whoisproxy.com
Contact emails
32e3e2fcb8@twitive.com.whoistrustee.com, 0c9c3ba1fcdef5701c1bdbb440da4f2dca272e158d9d46bb8a4cc57897db5d7d@twitive.com.whoisproxy.org, 3fc5f46782ff2057bc9bdc8ff56c0b6609d67770b629b96d419d657a9d46f77b@twitive.com.whoisproxy.org, 59ddc98494c67e8b7178d2d0f47876e9cabd99715767b97a1bc8260f21e87796@twitive.com.whoisproxy.org, 63f71fa2f5a7abc695ddc70e3f5fc853928088c48db65e0acda4cf5536cdcf0a@twitive.com.whoisproxy.org, 64e576d2557c0ad4c34b9b3a271de713c2ef5391875c51e7ba822e3f8c9bfdab@twitive.com.whoisproxy.org, bd5e69e9624754fb270e53ec04e25af64e4ec1cf478277bc22c65dc73ad896af@twitive.com.whoisproxy.org

Subdomains

Subdomain
en.twitive.com
es.twitive.com
m.twitive.com
n.twitive.com
support.twitive.com
wildcard.twitive.com

Showing 6 of 6 subdomains (6 per page).

Mail and authentication

Nameservers

  • luke.ns.cloudflare.com
  • nora.ns.cloudflare.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com
  • include: _spf.hyperowl.io

Threat-feed evidence

History

Related pages

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