Skip to content

Hostname

email.kickofflabs.com

Last fetched

email.kickofflabs.com resolves to 13.214.238.55, announced in 13.214.0.0/15 by AMAZON-02 - Amazon.com, Inc. in SG. email.kickofflabs.com is listed by 1 threat feed; reconciled level HIGH.

Threat posture

40threat score (procedure-native scale)

HIGH

Listed by 1 threat feed. At least one source recommends blocking.

Categories: Phishing

Threat feeds listing this
1
Verdict coverage
malicious-evidenced
First seen on a feed
Wed, 26 Aug 2026 14:49:49 GMT
Last seen on a feed
Tue, 22 Sep 2026 20:26:49 GMT

Nutrition Label

WHISPER CANON · email.kickofflabs.comRouting diversity2.4/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings8.0/10WHOIS transparency0.0/10Resolver footprint5.6/10canon.whisper.security/host/email.kickofflabs.com

Resolution chain

IPv6 resolution

No AAAA record for email.kickofflabs.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for email.kickofflabs.com. WHOIS is recorded against the registrable domain, so a subdomain such as a www. host carries none of its own — check the registrable domain for this name.

Subdomains

Showing 1 of 1 subdomain (1 per page).

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • ns10.dnsmadeeasy.com
  • ns11.dnsmadeeasy.com
  • ns12.dnsmadeeasy.com
  • ns13.dnsmadeeasy.com
  • ns14.dnsmadeeasy.com
  • ns15.dnsmadeeasy.com

MX records

  • mx.sendgrid.net
  • mx2.sendgrid.net

SPF policy

  • ip: 159.183.0.0/16
  • ip: 149.72.0.0/16
  • ip: 168.245.0.0/17
  • ip: 167.89.0.0/17
  • ip: 50.31.32.0/19
  • ip: 134.128.64.0/19
  • ip: 134.128.96.0/19
  • ip: 192.254.112.0/20
  • ip: 198.37.144.0/20
  • ip: 208.117.48.0/20
  • ip: 198.21.0.0/21
  • include: ab.sendgrid.net

Threat-feed evidence

History

Related pages

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