Hostname

patch-diff.githubusercontent.com

Last fetched Fri, 25 Sep 2026 05:54:38 GMT

patch-diff.githubusercontent.com resolves to 140.82.112.4, announced in 140.82.112.0/24 by GITHUB - GitHub, Inc. in US. patch-diff.githubusercontent.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

Resolution chain

IPv6 resolution

No AAAA record for patch-diff.githubusercontent.com is recorded in WhisperGraph.

Attribution

Github

saas · ORIGIN_AS

WHOIS identity

WhisperGraph holds no WHOIS registrar, registrant organisation or contact email for patch-diff.githubusercontent.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.

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

github.com

Mail and authentication

Nameservers

ns-421.awsdns-52.com
ns-520.awsdns-01.net
dns1.p08.nsone.net
dns2.p08.nsone.net
dns3.p08.nsone.net
dns4.p08.nsone.net
ns-1283.awsdns-32.org
ns-1707.awsdns-21.co.uk

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

ip: 192.30.252.0/22
ip: 167.89.101.192/28
ip: 192.254.112.98/31
include: _netblocks.google.com
include: _netblocks2.google.com
include: _netblocks3.google.com
include: mktomail.com
include: spf.protection.outlook.com
include: _spf.salesforce.com
include: mail.zendesk.com
include: servers.mcsv.net
ip: 166.78.69.169
ip: 166.78.69.170
ip: 166.78.71.131
ip: 167.89.101.2
ip: 192.254.112.60
ip: 192.254.113.10
ip: 192.254.113.101
ip: 192.254.114.176
ip: 62.253.227.114

Threat-feed evidence

History

Pivot from patch-diff.githubusercontent.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: "patch-diff.githubusercontent.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.