Skip to content

Hostname

warpdevelopment.com

Last fetched

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

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:69
Registrant organisation
warp development
Contact emails
aerasmus@warpdevelopment.co.za

Subdomains

Subdomain
autodiscover.warpdevelopment.com
jira.warpdevelopment.com
mta-sts.warpdevelopment.com
passer.warpdevelopment.com
proxy-fallback.warpdevelopment.com
remote.warpdevelopment.com
sip.warpdevelopment.com
staging.warpdevelopment.com
status.warpdevelopment.com
vod.warpdevelopment.com
vpn.warpdevelopment.com
www.warpdevelopment.com

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

  • seth.ns.cloudflare.com
  • tegan.ns.cloudflare.com

MX records

  • za-smtp-inbound-1.mimecast.co.za
  • za-smtp-inbound-2.mimecast.co.za

SPF policy

  • ip: 148.105.0.0/16
  • ip: 198.2.128.0/18
  • ip: 205.201.128.0/20
  • include: amazonses.com
  • include: _netblocks.mimecast.com
  • include: spf.protection.outlook.com
  • include: one.zoho.com
  • include: _spf.atlassian.net
  • include: servers.mcsv.net
  • include: zcsend.net
  • ip: 34.241.10.36
  • ip: 52.208.226.242

Threat-feed evidence

History

Related pages

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